Add support for Arista-7060X6-64PE-B-O128 TH5-512#22672
Merged
yxieca merged 5 commits intosonic-net:masterfrom Jun 5, 2025
Merged
Add support for Arista-7060X6-64PE-B-O128 TH5-512#22672yxieca merged 5 commits intosonic-net:masterfrom
yxieca merged 5 commits intosonic-net:masterfrom
Conversation
Collaborator
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
|
hi @rick-arista , what is the difference between this PR and this one? #22610 |
mssonicbld
added
Cherry Pick Conflict_msft-202412
and removed
Cherry Pick Conflict_msft-202412
labels
Contributor
Author
|
@r12f error on my part, this is the Arista-7060X6-64PE-O128, not the Arista-7060X6-64PE-O128S2. The symlink between the two will be removed from the other PR |
Collaborator
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
|
Thanks Rick! |
rick-arista
force-pushed
the
Arista-7060X6-64PE-O128S2-512
branch
from
f4d29c6 to
e26f528
Compare
Collaborator
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
|
@rick-arista Do you mind change the HWSKU name to |
12 tasks
Contributor
|
@rick-arista Is this PR ready for review? |
Contributor
Author
|
@bingwang-ms added a small fix just now. Ready for review |
Collaborator
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
|
Do you mind rename the HWSKU name to |
Collaborator
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
bingwang-ms
reviewed
May 27, 2025
Contributor
There was a problem hiding this comment.
Need another buffer config file for LT2.
For reference https://github.com/sonic-net/sonic-buildimage/blob/master/device/arista/x86_64-arista_7060x6_64pe/Arista-7060X6-64PE-O128S2/buffers_defaults_lt2.j2
bingwang-ms
reviewed
May 27, 2025
Contributor
There was a problem hiding this comment.
Need another cable length between LT2 and UT2
Contributor
Author
There was a problem hiding this comment.
@bingwang-ms I've added 150m, can you confirm this is correct?
Contributor
There was a problem hiding this comment.
There are 3 different cable length
- 5m
- 30m
- 500m
@kperumalbfn Please double confirm. Thanks
Contributor
|
@kperumalbfn Can you please help review? |
Collaborator
|
/azp run Azure.sonic-buildimage |
Collaborator
|
Cherry-pick PR to msft-202503: Azure/sonic-buildimage-msft#1205 |
yejianquan
added
Approved for 202505 Branch
and removed
Cherry Pick Conflict_202505
labels
Contributor
|
@rick-arista please fix the conflict and raise a PR to 202505 branch |
Contributor
|
11 tasks
Collaborator
|
Cherry-pick PR to msft-202412: Azure/sonic-buildimage-msft#1239 |
Contributor
|
Add label |
10 tasks
10 tasks
Contributor
|
New cherry-pick to 202412: Azure/sonic-buildimage-msft#1255 |
r12f
added a commit
to Azure/sonic-buildimage-msft
that referenced
this pull request
Jun 19, 2025
<!--
Please make sure you've read and understood our contributing guidelines:
https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md
** Make sure all your commits include a signature generated with `git
commit -s` **
If this is a bug fix, make sure your description includes "fixes #xxxx",
or
"closes #xxxx" or "resolves #xxxx"
Please provide the following information:
-->
#### Why I did it
Manual backport of
sonic-net/sonic-buildimage#22672 to address
missing LT2 template files in automerge PR:
#1239
##### Work item tracking
- Microsoft ADO **(number only)**:
#### How I did it
#### How to verify it
<!--
If PR needs to be backported, then the PR must be tested against the
base branch and the earliest backport release branch and provide tested
image version on these two branches. For example, if the PR is requested
for master, 202211 and 202012, then the requester needs to provide test
results on master and 202012.
-->
#### Which release branch to backport (provide reason below if selected)
<!--
- Note we only backport fixes to a release branch, *not* features!
- Please also provide a reason for the backporting below.
- e.g.
- [x] 202006
-->
- [ ] 201811
- [ ] 201911
- [ ] 202006
- [ ] 202012
- [ ] 202106
- [ ] 202111
- [ ] 202205
- [ ] 202211
#### Tested branch (Please provide the tested image version)
<!--
- Please provide tested image version
- e.g.
- [x] 20201231.100
-->
- [ ] <!-- image version 1 -->
- [ ] <!-- image version 2 -->
#### Description for the changelog
<!--
Write a short (one line) summary that describes the changes in this
pull request for inclusion in the changelog:
-->
<!--
Ensure to add label/tag for the feature raised. example - PR#2174 under
sonic-utilities repo. where, Generic Config and Update feature has been
labelled as GCU.
-->
#### Link to config_db schema for YANG module changes
<!--
Provide a link to config_db schema for the table for which YANG model
is defined
Link should point to correct section on
https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md
-->
#### A picture of a cute animal (not mandatory but encouraged)
r12f
added
Included in msft-202412 Branch
and removed
Created PR to msft-202412 Branch
labels
StormLiangMS
pushed a commit
that referenced
this pull request
Jul 7, 2025
… config file (#22998) Why I did it Recently we added stat_custom_receive0_management_mode config to TH5 Broadcom config files, and the changes upstreamed in #22825. There's a separate PR created to add new HWSKU Arista-7060X6-64PE-B-O128 around the same time, see #22672 As a result, stat_custom_receive0_management_mode was missed in Arista-7060X6-64PE-B-O128 config file. This change adds it. Work item tracking Microsoft ADO (number only): How I did it How to verify it Verified all interfaces are up with this change when using Arista-7060X6-64PE-B-O128
mssonicbld
added a commit
to mssonicbld/sonic-buildimage-msft
that referenced
this pull request
Jul 7, 2025
… config file
… config file
<!--
Please make sure you've read and understood our contributing guidelines:
https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md
** Make sure all your commits include a signature generated with `git commit -s` **
If this is a bug fix, make sure your description includes "fixes #xxxx", or
"closes #xxxx" or "resolves #xxxx"
Please provide the following information:
-->
#### Why I did it
Recently we added stat_custom_receive0_management_mode config to TH5 Broadcom config files, and the changes upstreamed in sonic-net/sonic-buildimage#22825.
There's a separate PR created to add new HWSKU Arista-7060X6-64PE-B-O128
around the same time, see sonic-net/sonic-buildimage#22672
As a result, stat_custom_receive0_management_mode was missed in Arista-7060X6-64PE-B-O128 config file. This change adds it.
##### Work item tracking
- Microsoft ADO **(number only)**:
#### How I did it
#### How to verify it
Verified all interfaces are up with this change when using Arista-7060X6-64PE-B-O128
<!--
If PR needs to be backported, then the PR must be tested against the base branch and the earliest backport release branch and provide tested image version on these two branches. For example, if the PR is requested for master, 202211 and 202012, then the requester needs to provide test results on master and 202012.
-->
#### Which release branch to backport (provide reason below if selected)
<!--
- Note we only backport fixes to a release branch, *not* features!
- Please also provide a reason for the backporting below.
- e.g.
- [x] 202006
-->
- [ ] 202205
- [ ] 202211
- [ ] 202305
- [ ] 202311
- [ ] 202405
- [ ] 202411
- [x] msft-202412
- [x] msft-202503
- [x] 202505
#### Tested branch (Please provide the tested image version)
<!--
- Please provide tested image version
- e.g.
- [x] 20201231.100
-->
- [x] msft-202412
#### Description for the changelog
<!--
Write a short (one line) summary that describes the changes in this
pull request for inclusion in the changelog:
-->
<!--
Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU.
-->
#### Link to config_db schema for YANG module changes
<!--
Provide a link to config_db schema for the table for which YANG model
is defined
Link should point to correct section on https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md
-->
#### A picture of a cute animal (not mandatory but encouraged)
10 tasks
mssonicbld
added a commit
to mssonicbld/sonic-buildimage
that referenced
this pull request
Jul 7, 2025
… config file
… config file
<!--
Please make sure you've read and understood our contributing guidelines:
https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md
** Make sure all your commits include a signature generated with `git commit -s` **
If this is a bug fix, make sure your description includes "fixes #xxxx", or
"closes #xxxx" or "resolves #xxxx"
Please provide the following information:
-->
#### Why I did it
Recently we added stat_custom_receive0_management_mode config to TH5 Broadcom config files, and the changes upstreamed in sonic-net#22825.
There's a separate PR created to add new HWSKU Arista-7060X6-64PE-B-O128
around the same time, see sonic-net#22672
As a result, stat_custom_receive0_management_mode was missed in Arista-7060X6-64PE-B-O128 config file. This change adds it.
##### Work item tracking
- Microsoft ADO **(number only)**:
#### How I did it
#### How to verify it
Verified all interfaces are up with this change when using Arista-7060X6-64PE-B-O128
<!--
If PR needs to be backported, then the PR must be tested against the base branch and the earliest backport release branch and provide tested image version on these two branches. For example, if the PR is requested for master, 202211 and 202012, then the requester needs to provide test results on master and 202012.
-->
#### Which release branch to backport (provide reason below if selected)
<!--
- Note we only backport fixes to a release branch, *not* features!
- Please also provide a reason for the backporting below.
- e.g.
- [x] 202006
-->
- [ ] 202205
- [ ] 202211
- [ ] 202305
- [ ] 202311
- [ ] 202405
- [ ] 202411
- [x] msft-202412
- [x] msft-202503
- [x] 202505
#### Tested branch (Please provide the tested image version)
<!--
- Please provide tested image version
- e.g.
- [x] 20201231.100
-->
- [x] msft-202412
#### Description for the changelog
<!--
Write a short (one line) summary that describes the changes in this
pull request for inclusion in the changelog:
-->
<!--
Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU.
-->
#### Link to config_db schema for YANG module changes
<!--
Provide a link to config_db schema for the table for which YANG model
is defined
Link should point to correct section on https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md
-->
#### A picture of a cute animal (not mandatory but encouraged)
10 tasks
mssonicbld
added a commit
that referenced
this pull request
Jul 9, 2025
… config file (#23243) … config file <!-- Please make sure you've read and understood our contributing guidelines: https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md failure_prs.log skip_prs.log Make sure all your commits include a signature generated with `git commit -s` ** If this is a bug fix, make sure your description includes "fixes #xxxx", or "closes #xxxx" or "resolves #xxxx" Please provide the following information: --> #### Why I did it Recently we added stat_custom_receive0_management_mode config to TH5 Broadcom config files, and the changes upstreamed in #22825. There's a separate PR created to add new HWSKU Arista-7060X6-64PE-B-O128 around the same time, see #22672 As a result, stat_custom_receive0_management_mode was missed in Arista-7060X6-64PE-B-O128 config file. This change adds it. ##### Work item tracking - Microsoft ADO **(number only)**: #### How I did it #### How to verify it Verified all interfaces are up with this change when using Arista-7060X6-64PE-B-O128 <!-- If PR needs to be backported, then the PR must be tested against the base branch and the earliest backport release branch and provide tested image version on these two branches. For example, if the PR is requested for master, 202211 and 202012, then the requester needs to provide test results on master and 202012. --> #### Which release branch to backport (provide reason below if selected) <!-- - Note we only backport fixes to a release branch, *not* features! - Please also provide a reason for the backporting below. - e.g. - [x] 202006 --> - [ ] 202205 - [ ] 202211 - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 - [x] msft-202412 - [x] msft-202503 - [x] 202505 #### Tested branch (Please provide the tested image version) <!-- - Please provide tested image version - e.g. - [x] 20201231.100 --> - [x] msft-202412 #### Description for the changelog <!-- Write a short (one line) summary that describes the changes in this pull request for inclusion in the changelog: --> <!-- Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU. --> #### Link to config_db schema for YANG module changes <!-- Provide a link to config_db schema for the table for which YANG model is defined Link should point to correct section on https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md --> #### A picture of a cute animal (not mandatory but encouraged)
r12f
pushed a commit
to Azure/sonic-buildimage-msft
that referenced
this pull request
Jul 9, 2025
…a-7060X6-64PE-B-O128 config file (#1321) … config file <!-- Please make sure you've read and understood our contributing guidelines: https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md ** Make sure all your commits include a signature generated with `git commit -s` ** If this is a bug fix, make sure your description includes "fixes #xxxx", or "closes #xxxx" or "resolves #xxxx" Please provide the following information: --> #### Why I did it Recently we added stat_custom_receive0_management_mode config to TH5 Broadcom config files, and the changes upstreamed in sonic-net/sonic-buildimage#22825. There's a separate PR created to add new HWSKU Arista-7060X6-64PE-B-O128 around the same time, see sonic-net/sonic-buildimage#22672 As a result, stat_custom_receive0_management_mode was missed in Arista-7060X6-64PE-B-O128 config file. This change adds it. ##### Work item tracking - Microsoft ADO **(number only)**: #### How I did it #### How to verify it Verified all interfaces are up with this change when using Arista-7060X6-64PE-B-O128 <!-- If PR needs to be backported, then the PR must be tested against the base branch and the earliest backport release branch and provide tested image version on these two branches. For example, if the PR is requested for master, 202211 and 202012, then the requester needs to provide test results on master and 202012. --> #### Which release branch to backport (provide reason below if selected) <!-- - Note we only backport fixes to a release branch, *not* features! - Please also provide a reason for the backporting below. - e.g. - [x] 202006 --> - [ ] 202205 - [ ] 202211 - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 - [x] msft-202412 - [x] msft-202503 - [x] 202505 #### Tested branch (Please provide the tested image version) <!-- - Please provide tested image version - e.g. - [x] 20201231.100 --> - [x] msft-202412 #### Description for the changelog <!-- Write a short (one line) summary that describes the changes in this pull request for inclusion in the changelog: --> <!-- Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU. --> #### Link to config_db schema for YANG module changes <!-- Provide a link to config_db schema for the table for which YANG model is defined Link should point to correct section on https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md --> #### A picture of a cute animal (not mandatory but encouraged)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
11 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why I did it
Add support for Arista-7060X6-64PE-O128 TH5-512
Work item tracking
How I did it
How to verify it
Which release branch to backport (provide reason below if selected)
Tested branch (Please provide the tested image version)
Description for the changelog
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)